src/utils/accountDisplay.ts (1)

1-45: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Consider adding unit tests for the initials/display-name branching logic.

Several edge cases (missing names, whitespace-only names, single vs. multi-part email local-parts) are handled correctly, but the branching is non-trivial and easy to regress silently.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/accountDisplay.ts` around lines 1 - 45, Add unit tests for the
branching in getAccountDisplayName and getAccountInitials in accountDisplay.ts,
covering missing names, whitespace-only first/last names, email fallback
behavior, and both single-part and multi-part email local-parts. Use the public
helpers getAccountDisplayName, getAccountInitials, and the internal behaviors
around buildEmailFallback/firstCharacter as the cases to verify so regressions
in these edge paths are caught.

src/app/screens/DraftingScreen.tsx (1)

22-24: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Remove leftover commented-out code.

// useDraftingContext, and {/* <DraftingPlayerBar verses={verses} /> */} are dead code left in from the refactor.

🧹 Cleanup

 import {
   DraftingProvider,
-  // useDraftingContext,

-          {/* <DraftingPlayerBar verses={verses} /> */}
-

Also applies to: 200-200

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/screens/DraftingScreen.tsx` around lines 22 - 24, Remove the leftover
commented-out code from the Drafting screen refactor. In DraftingScreen, delete
the unused commented import `useDraftingContext` and the commented JSX for
`DraftingPlayerBar`, keeping only the active imports and rendered components.
Use the identifiers DraftingScreen, DraftingProvider, useDraftingContext, and
DraftingPlayerBar to locate the dead code and clean it out.

src/components/ui/AccountSwitcherPanel.tsx (2)

47-53: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Backdrop Pressable may swallow taps on non-interactive sheet areas.

The sheet body (Line 48) is a plain View nested inside the backdrop Pressable. Taps on padding/gaps within the sheet (not on a TouchableOpacity) will likely bubble up and trigger onClose, closing the modal unexpectedly.

🔧 Proposed fix to stop propagation on the sheet

-        <View
+        <Pressable
+          onPress={() => {}}
           style={[
             styles.sheet,
             { paddingBottom: insets.bottom + theme.spacing.lg },
           ]}
         >
           ...
-        </View>
+        </Pressable>

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/ui/AccountSwitcherPanel.tsx` around lines 47 - 53, The
backdrop Pressable in AccountSwitcherPanel is wrapping the entire sheet, so taps
on non-interactive areas inside the sheet can still trigger onClose. Move the
close handler to the backdrop only and stop touch propagation for the sheet
container itself, using the existing Pressable/View structure around
styles.backdrop and styles.sheet so taps inside the sheet body do not dismiss
the modal unexpectedly.

---

160-161: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Hardcoded hex/rgba colors alongside theme tokens.

'rgba(10, 18, 40, 0.44)', '#F3F7FF', '#2E5BD8', '#F1F4FA' are hardcoded even though the rest of the stylesheet consistently uses theme.colors.*. Consider adding equivalent theme tokens for consistency and easier future theming (e.g., dark mode).

Also applies to: 208-211, 222-223, 266-267

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/ui/AccountSwitcherPanel.tsx` around lines 160 - 161, Replace
the remaining hardcoded color values in AccountSwitcherPanel’s stylesheet with
theme-backed values to match the existing `theme.colors.*` pattern. Update the
styles around the background and text/border states referenced in
`AccountSwitcherPanel` (including the selection, hover, and divider-related
styles) so they use equivalent tokens instead of `rgba(10, 18, 40, 0.44)`,
`#F3F7FF`, `#2E5BD8`, and `#F1F4FA`. If matching tokens do not exist yet, add
them to the theme and then consume them here.

src/hooks/useActiveAccountSummary.ts (1)

25-41: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Duplicated cancellation-guard boilerplate across hooks.

The mountedRef/requestIdRef setup and cleanup effect (Lines 29-37) is duplicated almost verbatim in src/hooks/useDeviceAccounts.ts (Lines 33-41). Consider extracting a small shared hook (e.g. useCancellableAsync() returning { mountedRef, nextRequestId }) to keep the guard logic consistent and avoid maintaining it in two places.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useActiveAccountSummary.ts` around lines 25 - 41, The
mountedRef/requestIdRef cancellation guard in useActiveAccountSummary is
duplicated in useDeviceAccounts, so extract the shared lifecycle/request
tracking into a small reusable hook such as useCancellableAsync that exposes the
mounted state and a nextRequestId helper. Then update useActiveAccountSummary
and useDeviceAccounts to consume that shared hook instead of each defining their
own refs and cleanup effect, keeping the cancellation logic centralized and
consistent.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes